-
Notifications
You must be signed in to change notification settings - Fork 176
conformance: Rename infra namespace #1667
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
@davidjumani: The label(s) In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: davidjumani The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
✅ Deploy Preview for gateway-api-inference-extension ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
@davidjumani did you run the conformance test suite after making these changes? If not, you can follow these steps and instead of calling $ go test -v ./conformance -args -debug=true -gateway-class=kgateway |
I initially verified the change via the make command. Running it again and all passed
Some logs to indicate that the ns has indeed changed
|
What type of PR is this?
Add one of the following kinds:
/kind cleanup
Optionally add one or more of the following kinds if applicable:
/area conformance-test
What this PR does / why we need it:
This renames the inference conformance infra from
gateway-conformance-infra
toinference-conformance-infra
.This allows clean back-to-back runs of the Gateway API and Inference Extension conformance tests avoiding any failures caused by using the same namespace
Which issue(s) this PR fixes:
Fixes #1315
Does this PR introduce a user-facing change?: